Issue:

When processing a COPY record through the resolve migrations pipeline, the booking's scheduledFor and the capture session's startedAt/finishedAt timestamps are incorrectly overwritten with the COPY's values. COPY records reuse the original record's booking and capture session, so these fields should be preserved - but instead they get replaced with different values from the COPY.

Fix:

For COPY records, the existing booking's scheduledFor and the existing capture session's startedAt, finishedAt, startedByUserId, and finishedByUserId are now fetched and preserved rather than being overwritten. For ORIG (non-COPY) records, behaviour is unchanged.

Test plan:

[ x ] Migrate an ORIG recording and verify scheduledFor and capture session timestamps are set correctly from the archive name
[ x ] Migrate a COPY record for the same booking via the resolve migrations pipeline and verify scheduledFor and capture session timestamps remain unchanged from the original